 |
|
| If you can't view the Datasheet, Please click here to try to view without PDF Reader . |
|
|
|
| If you can't view the Datasheet, Please click here to try to view without PDF Reader . |
|
|
| Datasheet File OCR Text: |
| ? integrated circuits group lh 28 f 16 0 s 5 ns - l 7 0 fla sh me mor y 16 m ( 2 m b 8 / 1 mb 16 ) (model no.: lh f 16 ka 4 ) spec no.: el 1 2 80 40 issue date: a ugu st 2 2 , 20 0 0 p roduc t s pecific a tions
sharp lhf16ka4 . - l handle this document carefully for it contains material protected by international copyright law. any reproduction, full or in part, of this material is prohibited without the express written permission of the company. l when using the products covered herein, please observe the conditions written herein and the precautions outlined in the following paragraphs. in no event shall the company be liable for any damages resulting from failure to strictly adhere to these conditions and precautions. (1) the products covered herein are designed and manufactured for the following application areas. when using the products covered herein for the equipment listed in paragraph (2), even for the following application areas, be sure to observe the precautions given in paragraph (2). never use the products for the equipment listed in paragraph (3). aoffice electronics ? l instrumentation and measuring equipment l machine tools *audiovisual equipment *home appliance *communication equipment other than for trunk lines (2) those contemplating using the products covered herein for the following equipment which demands high reliability, should first contact a sales representative of the company and then accept responsibility for incorporating into the design fail-safe operation, redundancy, and other appropriate measures for ensuring reliability and safety of the equipment and the overall system. *control and safety devices for airplanes, trains, automobiles, and other transportation equipment *mainframe computers *traffic control systems agas leak detectors and automatic cutoff devices *rescue and security equipment l other safety devices and safety equipment, etc. (3) do not use the products covered herein for the following equipment which demands extremely high performance in terms of functionality, reliability, or accuracy. *aerospace equipment l communications equipment for trunk lines *control equipment for the nuclear power industry amedical equipment related to life support, etc. (4) please direct all queries and comments regarding the interpretation of the above three paragraphs to a sales representative of the company. l please direct all queries regarding the products covered herein to a sales representative of the company. rev.1.9 shal?p lhflgka4 1 . - -- - contents page page 1 introduction ...................................................... 3 1 .l product overview ................................................ 3 2 principles of operation ................................ 6 2.1 data protection ................................................... 7 3 bus operation.. .................................................. 7 3.1 read ................................................................... 7 3.2 output disable .................................................... 7 3.3 standby ............................................................... 7 3.4 deep power-down .............................................. 7 3.5 read identifier codes operation.. ....................... 8 3.6 query operation .................................................. 8 3.7 write.. .................................................................. 8 5 design considerations ................................ .30 5.1 three-line output control ................................ .30 5.2 sts and block erase, full chip erase, (multi) word/byte write and block lock-bit configuration polling.. ............................................................. .30 5.3 power supply decoupling.. ............................... .30 5.4 v,, trace on printed circuit boards.. ............... .30 5.5 v,,, v,,, rp# transitions.. .............................. .31 5.6 power-up/down protection.. ............................. .31 5.7 power dissipation ............................................. .31 6 electrical specifications.. ........................ .32 6.1 absolute maximum ratings .............................. .32 6.2 operating conditions ........................................ .32 6.2.1 capacitance ................................................ .32 4 command definitions ....................................... 8 6.2.2 ac input/output test conditions.. ............... .33 4.1 read array command.. ..................................... 1 1 6.2.3 dc characteristics.. ..................................... .34 4.2 read identifier codes command.. .................... 11 6.2.4 ac characteristics - read-only operations .36 4.3 read status register command.. 11 6.2.5 ac characteristics - write operations.. ....... .39 ..................... 4.4 clear status register command.. 11 6.2.6 alternative ce#-controlled writes.. ............. .41 ..................... 4.5 query command 12 6.2.7 reset operations ........................................ .43 ............................................... 4.5.1 block status register .................................. 12 6.2.8 block erase, full chip erase, (multi) 4.5.2 cfi query identification string.. ................... 13 word/byte write and block lock-bit 4.5.3 system interface information.. ..................... 13 configuration performance.. ........................ .44 4.5.4 device geometry definition ......................... 14 4.5.5 scs oem specific extended query table . . 14 7 additional information ................................ 45 4.6 block erase command.. .................................... 15 7.1 ordering information .......................................... 45 4.7 full chip erase command ................................ 15 - 4.8 word/byte write command.. ............................. 16 4.9 multi word/byte write command.. .................... 16 4.10 block erase suspend command.. ................... 17 4.11 (multi) word/byte write suspend command ... 17 4.12 set block lock-bit command.. ........................ 18 4.13 clear block lock-bits command.. ................... 18 4.14 sts configuration command ......................... 19 rev. 1.9 shafzp lhf16ka4 2 - lh28f160s5nsl70 1 gm-bit (2mbx8/1 mbxl6) smart 5 flash memory i smart 5 technology - 5v vcc - sv vpp n common flash interface (cfi) - universal & upgradable interface n enhanced data protection features - absolute protection with vpp=gnd - flexible block locking - erase/write lockout during power transitions n scalable command set (scs) n extended cycling capability - 100,000 block erase cycles n high speed write performance - 3.2 million block erase cycles/chip - 32?bytes x 2 plane page buffer - 2pslbyte write transfer rate n low power management - deep power-down mode i high speed read performance - automatic power savings mode - 70ns(sv*o.25!/), 80ns(5v*osv) decreases icc in static mode i operating temperature n automated write and erase - 0c to +7o?c - command user interface i enhanced automated suspend options - status register - write suspend to read n industry-standard packaging - block erase suspend to write - 56-lead ssop - block erase suspend to read n etoxtm? v nonvolatile flash i high-density symmetrically-blocked technology architecture - thirty-two 64k-byte erasable blocks n cmos process (p-type silicon substrate) n sram-compatible write interface n user-configurable x8 or x16 operation n not designed or rated as radiation hardened sharp?s LH28F160S5NS-L70 flash memory with smart 5 technology is a high-density, low-cost, nonvolatile, read/write storage solution for a wide range of applications. its symmetrically-blocked architecture, flexible voltage snd extended cycling provide for highly flexible component suitable for resident flash arrays, slmms and memory :ards. its enhanced suspend capabilities provide for an ideal solution for code + data storage applications. for secure code storage applications, such as networking, where code is either directly executed out of flash or downloaded to dram, the lh28f160s5nsl70 offers three levels of protection: absolute protection with v,, at snd, selective hardware block locking, or flexible software block locking. these alternatives give designers jltimate control of their code security needs. the LH28F160S5NS-L70 is conformed to the flash scalable command set (scs) and the common flash interface cfi) specification which enable universal and upgradable interface, enable the highest system/device data transfer ?ates and minimize device and system-level implementation costs. the LH28F160S5NS-L70 is manufactured on sharp?s 0.35um etox tm* v process technology. it come in ndustry-standard package: the 56-lead ssop, ideal for board constrained applications. ?etox is a trademark of intel corporation. rev. 1.9 sharp lhf16ka4 3 . - 1 introduction execute code from any other flash memory array location. this datasheet contains lh28f160ssnsl70 specifications. section 1 provides a flash memory overview. sections 2, 3, 4, and 5 describe the memory organization and functionality. section 6 covers electrical specifications. 1 .l product overview the lh28f160s5nsl70 is a high-performance 16m- bit smart 5 flash memory organized as 2mbx8/1 mbxl6. the 2mb of data is arranged in thirty-two 64k-byte blocks which are individually erasable, lockable, and unlockable in-system. the memory map is shown in figure 3. smart 5? technology provides a choice of vc, and v,, combinations, as shown in table 1, to meet system performance and power expectations. 5v vo, provides the highest read performance. v,, at 5v eliminates the need for a separate 12v converter, while v,,=5v maximizes erase and write performance. in addition to flexible erase and program voltages, the dedicated v,, pin gives complete data protection when v+v,,l,. table 1. v,, and vp, voltage combinations offered by smart 5 technology vcc voltage vpp voltage e;v !iv internal vco . and vw detection circuitry automatically configures the device for optimized read and write operations. .i? a command user interface (cui) serves as the interface between the system processor and internal operation of the device. a valid command sequence written to the cui initiates device automation. an internal write state machine (wsm) automatically executes the algorithms and timings necessary for block erase, full chip erase, (multi) word/byte write and block lock-bit configuration operations. a block erase operation erases one of the device?s wk-byte blocks typically within 0.34s (5v vco, 5v v,,) independent of other blocks. each block can be independently erased 100,000 times (3.2 million block erases per device). block erase suspend mode allows system software to suspend block erase to read or write data from any other block. a word/byte write is performed in byte increments typically within 9.24us (5v voc, 5v v,,). a multi word/byte write has high speed write performance of 2uslbyte (5v voc, 5v v,,). (multi) word/byte write suspend mode enables the system to read data or individual block locking uses a combination of bits and wp#, thirty-two block lock-bits, to lock and unlock blocks. block lock-bits gate block erase, full chip erase and (multi) word/byte write operations. block lock-bit configuration operations (set block lock-bit and clear block lock-bits commands) set and cleared block lock-bits. the status register indicates when the wsm?s block erase, full chip erase, (multi) word/byte write or block lock-bit configuration operation is finished. the sts output gives an additional indicator of wsm activity by providing both a hardware signal of status (versus software polling) and status masking (interrupt masking for background block erase, for example). status polling using sts minimizes both cpu overhead and system power consumption. sts pin can be configured to different states using the configuration command. the sts pin defaults to ry/by# operation. when low, sts indicates that the wsm is performing a block erase, full chip erase, (multi) word/byte write or block lock-bit configuration. sts-high z indicates that the wsm is ready for a new command, block erase is suspended and (multi) word/byte write are inactive, (multi) word/byte write are suspended, or the device is in deep power-down mode. the other 3 alternate configurations are all pulse mode for use as a system interrupt. the access time is 70ns (tavqv) over the commercial temperature range (0c to +7o?c) and v,, supply voltage range of 4.75v-5.25v. at lower v,-c voltage, the access time is 80ns (4.5v-5.5v). the automatic power savings (aps) feature substantially reduces active current when the device is in static mode (addresses not switching). in aps mode, the typical icon current is 1 ma at 5v v,,. when either cec# or ce,#, and rp# pins are at vcc, the icc cmos standby mode is enabled. when the rp# pin is at gnd, deep power-down mode is enabled which minimizes power consumption and provides write protection during reset. a reset time (tphqv) is required from rp# switching high until outputs are valid. likewise, the device has a wake time (tphel) from rp#-high until writes to the cui are recognized. with rp# at gnd, the wsm is reset and the status register is cleared. the device is available in 56-lead ssop (shrink small outline package). pinout is shown in figure 2. rev. 1.9 sharf= lhflgka4 4 l _- figure 1. block diagram _ cen,# a12. a13. / a14 4s c$ nc a20 49 ale a17 4s vcc gnd dq6 dq14 dq7 dqls sts oe# we# wp# dqn dq5 dq12 dq4 vcc 56 lead ssqp 1.8mm x 16mm x 23.7mm top view vpp rp# 41 40 a9 al a2 i$ 43 a7 gnd 43 vcc dqg dqi dqa dqo 43 byte# nc 2, dqlo dq3 dqii gnd figure 2. ssop 56-lead pinout rev. 1.9 shari= lhf16ka4 5 . - c -- - table 2. pin descriptions symbol type name and function address inputs: inputs for addresses during read and write operations. addresses are internally latched during a write cycle. a0420 input ao: byte select address. not used in x16 mode(can be floated). ai-ak column address. selects 1 of 16 bit lines. a5-a15: row address. selects 1 of 2048 word lines. air+a20 : block address. data input/outputs: dqo-dq7:lnputs data and commands during cui write cycles; outputs data during memory array, status register, query, and identifier code read cycles. data pins float to high- input/ impedance when the chip is deselected or outputs are disabled. data is internally latched )qo-dc&5 output during a write cycle. ce,#, ce,# dqs-dqt5:lnputs data during cui write cycles in xl 6 mode; outputs data during memory array read cycles in xl 6 mode; not used for status register, query and identifier code read mode. data pins float to high-impedance when the chip is deselected, outputs are disabled, or in x8 mode(byte#=v,, ). data is internally latched during a write cycle. chip enable: activates the device?s control logic, input buffers decoders, and sense input amplifiers. either ce,# or ce,# v,, deselects the device and reduces power consumption to standby levels. both cer,# and ce,# must be v,, to select the devices. reset/deep power-down: puts the device in deep power-down mode and resets rp# oe# we# sts input internal automation. rp# v,, enables normal operation. when driven v,,, rp# inhibits write operations which provides data protection during power transitions. exit from deep power-down sets the device to read array mode. input output enable: gates the device?s outputs during a read cycle. input write enable: controls writes to the cui and array blocks. addresses and data are latched on the rising edge of the we# pulse. sts (ry/by#): indicates the status of the internal wsm. when configured in level mode (default mode), it acts as a ry/by# pin. when low, the wsm is performing an internal open operation (block erase, full chip erase, (multi) word/byte write or block lock-bit drain configuration). sts high z indicates that the wsm is ready for new commands, block output erase is suspended, and (multi) word/byte write is inactive, (multi) word/byte write is suspended or the device is in deep power-down mode. for alternate configurations of the ?status pin, see the configuration command. wp# input write protect: master control for block locking. when v,,, locked blocks can not be erased and programmed, and block lock-bits can not be set and reset. byte enable: byte# v,, places device in x8 mode. all data is then input or output on byte# input dqo-,, and dqs-,5 float. byte# v,, places the device in xl 6 mode , and turns off the a, input buffer. vpp block erase, full chip erase, (multi) word/byte write, block lock- bit configuration power supply: for erasing array blocks, writing bytes or supply configuring block lock-bits. with v+v~~xl~, memory contents cannot be altered. block erase, full chip erase, (multi) word/byte write and block lock-bit configuration with an invalid vpp (see dc characteristics) produce spurious results and should not be attempted. device power supply: internal detection configures the device for 5v operation. do vcc gnd nc supply not float any power pins. with vc,iv,ko, all write attempts to the flash memory are inhibited. device operations at invalid voo voltage (see dc characteristics) produce spurious results and should not be attempted. supply ground: do not float any ground pins. no connect: lead is not internal connected; it may be driven or floated. rev. 1.9 sharp . lhf16ka4 6 . - .- - 2 principles of operation the LH28F160S5NS-L70 flash memory includes an on-chip wsm to manage block erase, full chip erase, (multi) word/byte write and block lock-bit configuration functions. it allows for: 100% ttl-level control inputs, fixed power supplies during block erase, full chip erase, (multi) word/byte write and block lock-bit configuration, and minimal processor overhead with ram-like interface timings. after initial device power-up or return from deep power-down mode (see bus operations), the device defaults to read array mode. manipulation of external memory control pins allow array read, standby, and output disable operations. status :egister, query structure and identifier codes can be accessed through the cui independent of the vp, voltage. high voltage on vp, enables successful block erase, full chip erase, (multi) word/byte write and block lock-bit configuration. all functions associated with altering memory contents-block erase, full chip erase, (multi) word/byte write and block lock-bit configuration, status, query and identifier codes-are accessed via the cui and verified through the status register. commands are written using standard microprocessor write timings. the cui contents serve as input to the wsm, which controls the block erase, full chip erase, (multi) word/byte write and block lock- bit configuration. the internal algorithms are regulated by the wsm, including pulse repetition, internal verification, and margining of data. addresses and data are internally latch during write cycles. writing the appropriate command outputs array data, accesses the identifier codes, outputs query structure or outputs status register data. interface software that initiates and polls progress of block erase, full chip erase, (multi) word/byte write and block lock-bit configuration can be stored in any block. this code is copied to and executed from system ram during flash memory updates. after successful completion, reads are again possible via the read array command. block erase suspend allows system software to suspend a block erase to read or write data from any other block. write suspend allows system software to suspend a (multi) word/byte write to read data from any other flash memory array location. i foooo 1 effff 1 eoooji 1 dffff 1 lioogq 1cffff 1c0ooa 1 bffff lbo@jo iaffff iaowo isffff iwooo ieffff 160000 17ffff 17ocoo igffff 16omm 1 sffff 150000 14ffff 14omx) 1 bffff 13oooo ipffff 120coo 1 iffff iiowo 1offff iwoqo offfff of0000 oeffff oeoooo odffff ollogao ocffff ocoooo obffff 0b0000 oaffff oaoooo osffff 09chy30 obffff otlmmo 07ffff 07ccoo ogffff 06woo osffff o5oooo 04ffff 040000 obffff 03cooo opffff ozoooo 01 ffff 01oaj0 ooffff figure 3. memory map rev. 1.9 sharp lhf16ka4 7 . - 2.1 data protection 3.2 output disable depending on the application, the system designer may choose to make the vpp power supply switchable (available only when block erase, full chip erase, (multi) word/byte write and block lock-bit configuration are required) or hardwired to v,,,,. the device accommodates either design practice and encourages optimization of the processor-memory interface. when vpplvpplk, memory contents cannot be altered. the cui, with multi-step block erase, full chip erase, (multi) word/byte write and block lock-bit configuration command sequences, provides protection from unwanted operations even when high voltage {is applied to v,,. all write functions are disabled when vcc is below the write lockout voltage v,,, or when rp# is at v,,. the device?s block locking capability provides additional protection from inadvertent code or data alteration by gating block erase, full chip erase and (multi) word/byte write operations. 3 bus operation the local cpu reads and writes flash memory in- system. all bus cycles to or from the flash memory conform to standard microprocessor bus cycles. 3.1 read information can be read from any block, identifier codes, query structure,?.or status register independent of the v,, voltage. rp# must be at vi,. the first task is to write the appropriate read mode command (read array, read identifier codes, query or read status register) to the cui. upon initial device power-up or after exit from deep power-down mode, the device automatically resets to read array mode. five control pins dictate the data flow in and out of the component: ce# (ce,#, ce,#), oe#, we#, rp# and wp#. ce,#, ce,# and oe# must be driven active to obtain data at the outputs. ce,#, ce,# is the device selection control, and when active enables the selected memory device. oe# is the data output (dqc-dq,s) control and when active drives the selected memory data onto the i/o bus. we# and rp# must be at v,,. figure 17, 18 illustrates a read cycle. with oe# at a logic-high level (vi,), the device outputs are disabled. output pins dc&,-dq,, arc placed in a high-impedance state. 3.3 standby either ce,# or ce,# at a logic-high level (v,,) places the device in standby mode which substantially reduces device power consumption. dq,-dq,, outputs are placed in a high-impedance state independent of oe#. if deselected during block erase, full chip erase, (multi) word/byte write ant block lock-bit configuration, the device continues functioning, and consuming active power until the operation completes. 3.4 deep power-down rp# at v,, initiates the deep power-down mode. in read modes, rp#-low deselects the memory places output drivers in a high-impedance state ant turns off all internal circuits. rp# must be held low for a minimum of 100 ns. time tphqv is required after return from power-down until initial memory access outputs are valid. after this wake-up interval, norma operation is restored. the cui is reset to read array mode and status register is set to 80h. during block erase, ?full chip erase, (multi) word/byte write or block lock-bit configuration modes, rp#-low will abort the operation. sts remains low until the reset operation is complete. memory contents being altered are no longer valid; the data may be partially erased or written. time tphwl is required after rp# goes to logic-high (v,,) before another command can be written. as with any automated device, it is important tc assert rp# during system reset. when the system comes out of reset, it expects to read from the flash memory. automated flash memories provide status information when accessed during block erase, full chip erase, (multi) word/byte write and block lock-bit configuration. if a cpu reset occurs with no flash memory reset, proper cpu initialization may no! occur because the flash memory may be providing status information instead of array data. sharp?s flash memories allow proper cpu initialization following a system reset through the use of the rp# input. in this application, rp# is controlled by the same reset# signal that resets the system cpu. rev. 1.9 shari= lhf16ka4 a 3.5 read identifier codes operation 3.6 query operation the read identifier codes operation outputs the manufacturer code, device code, block status codes for each block (see figure 4). using the manufacturer and device codes, the system cpu can automatically match the device with its proper algorithms. the block status codes identify locked or unlocked block setting and erase completed or erase uncompleted condition. the query operation outputs the query structure. query database is stored in the 48byte rom. query structure allows system software to gain critical information for controlling the flash component. query structure are always presented on the lowest- order data output (dqc-dq,) only. 3.7 write 1fffff 1 if0006 1 foo05 1 fooq4 1 foo03 1foooo 1 effff 020000 01 ffff ? :. ?&tie. l~plementation ?.. 01ochx~ ? 010005 010004 .; t-----------------------t-------------- ml ~? 31 status code ----------------------- reserved fbr ~tufe fmplementation ? block 31 3locks2thiw$i30) : 4. resewed. far future tmplementation ----------. 010003 i ovlooo i ft ooffff i i block 1 status code _----------------- ------- bsatnted for ?.. rture lmpl&w4~tion : / mock i ___----------------- ._______ ----------------------- n?- -i- ?i status code :ode manut ?- - ?acturer code black 0 figure 4. device identifier code memory map writing commands to the cui enable reading of device data and identifier codes. they also control inspection and clearing of the status register. when vcc=vcc1,2 and vpp=vpphi, the cui additionally controls block erase, full chip erase, (multi) word/byte write and block lock-bit configuration. the block erase command requires appropriate command data and an address within the block to be erased. the word/byte write command requires the command and address of the location to be written. set block lock-bit command requires the command and block address within the device (block lock) to be locked. the clear block lock-bits command requires the command and address within the device. the cui does not occupy an addressable memory location. it is written when we# and ce# are active. the address and data needed to execute a command are latched on the rising edge of we# or ce# (whichever goes high first). standard microprocessor write timings are used. figures 19 and 20 illustrate we# and ce#-controlled write operations. 4 command definitions when the v,, voltage i v,,,,, read operations from the status register, identifier codes, query, or blocks are enabled. placing v,,,, on v,, enables successful block erase, full chip erase, (multi) word/byte write and block lock-bit configuration operations. device operations are selected by writing specific commands into the cui. table 4 defines these commands. rev. 1.9 sliarp lhflgka4 9 - table 3. bus oderations(byte#=viui mode notes rp# ce?# ce,# oe# we# address vpp dq0.,5 sts read 1,2,3,9 v,h v,, v,, v,, v,h x x dn,,r x output disable 3 v,w v,, v,, v,h v,m x x high z x vi, vlh standby 3 vi, 4, x x x x high z x v,h deep power-down 4 read identifier codes query v,, x~ x- x x x x high z high z 9 vi, yl 4, vi, vlh see figure 4 x note 5 high z 9 vi, vi, vi, vi, vi, see table x 7-11 note 6 high z i i i i i i i i write 13,7,8,9 1 v,h 1 vi, 1 v,, 1 v,i-i 1 v,, 1 i 1 x 1 din 1 x deep power-down read identifier codes 4 v,, x x x x x x high z high z 9 ?ih vi, vi, vi, vlh see figure 4 x note 5 high z query write iotes: 9 vlh vi, 3,7,8,9 vih v,, vi, v,, vi, vlh see table x 7-11 note 6 high z v,h v,, x x din x i. refer to dc characteristics. when vpplvpplk, memory contents can be read, but not altered. !. x can be vi, or vi, for control pins and addresses, and v,,,, or vp,,, for v,,. see dc characteristics for v,,,, and vp,,, voltages. !. sts is vo, (if configured to ry/by# mode) when the wsm is executing internal block erase, full chip erase, (multi) word/byte write or block lock-bit configuration algorithms. it is floated during when the wsm is not busy, in block erase suspend mode with (multi) word/byte write inactive, (multi) word/byte write suspend mode, or deep powegdown mode. 8 i. rp# at gndfl.2v ensures the lowest deep power-down current. i. see section 4.2 for read identifier code data. i. see section 4.5 for query data. ?. command writes involving block erase, full chip erase, (multi) word/byte write or block lock-bit configuration are reliably executed when vpp=vprzzht and vco=voo1,2. i. refer to table 4 for valid d,, during a write operation. l don?t use the timing both oe# and we# are v,,. rev. 1.9 shai?l= . . lhflgka4 10 command read array/reset read identifier codes query read status register clear status reaister table 4. command definitions(lo) bus cycles notes first bus cycle second bus cycle req?d oper(?) 1 addr(*) 1 data13) oper(?) 1 addr(*) datat3) 1 write 1 x 1 ffh ia id , sa qd 70h 1 read 1 x srd 50h 1 22 4 write x 22 write x 2 write x i 1 i i write i x i block erase setup/confirm full chip erase setup/confirm word/byte write setup/write alternate word/byte write setuomlrite 2 5 write ba 20h write ba doh 2 write x 30h write x doh 2 56 write wa 40h write wa wd r) cc \a/ritn wa 10h write wa wd multi word/byte write setuokonfirm block erase and (multi) word/byte write suspend confirm and block erase a \alrita wa e8h write wa n-l e \a/&m 1 x boh and (multi) word/byte write resume block lock-bit set setup/confirm block lock-bit reset setup/confirm sts configuration level-mode for erase and write 1 5 write x doh 2 7 write ba 60h write ba olh 2 8 write x 60h write x doh 2 write x b8h write x ooh (ry/by# mode) sts configuration pulse-mode for erase sts configuration pulse-mode for write sts configuration pulse-mode for erase i i i i i i i i i write write and write 2 x el! x x write write write write notes: 1. bus operations are defined in table 3 and table 3.1. 2. x=any valid address within the device. ia=ldentifier code address: see figure 4. qa=query offset address. ba=address within theblock being erased or locked. wa=address of memory location to be written. 3. srd=data read from status register. see table 14 for a description of the status register bits. wd=data to be written at location wa. data is latched on the rising edge of we# or ce# (whichever goes high first). id=data read from identifier codes. qd=data read from query database. 4. following the read identifier codes command, read operations access manufacturer, device and block status codes. see section 4.2 for read identifier code data. 5. if the block is locked, wp# must be at vi, to enable block erase or (multi) word/byte write operations. attempts to issue a block erase or (multi) word/byte write to a locked block while rp# is vi,. 6. either 40h or 10h are recognized by the wsm as the byte write setup. 7. a block lock-bit can be set while wp# is vi,. 8. wp# must be at vi, to clear block lock-bits. the clear block lock-bits operation simultaneously clears all block lock-bits. 9. following the third bus cycle, inputs the write address and write data of ?n? times. finally, input the confirm command ?doh?. 10. commands other than those shown above are reserved by sharp for future device implementations and should not be used. rev. 1.9 sharp . - lhflgka4 11 - 4.1 read array command upon initial device power-up and after exit from deep power-down mode, the device defaults to read array mode. this operation is also initiated by writing the read array command. the device remains enabled for reads until another command is written. once the internal wsm has started a block erase, full chip erase, (multi) word/byte write or block lock-bit configuration, the device will not recognize the read array command until the wsm completes its operation unless the wsm is suspended via an erase suspend and (multi) word/byte write suspend command. the read array command functions independently of the v,, voltage and rp# must be vi,- 4.2 &ad identifier codes command the identifier code operation is initiated by writing the read identifier codes command. following the command write, read cycles from addresses shown in figure 4 retrieve the manufacturer, device, block lock configuration and block erase status (see table 5 for identifier code values). to terminate the operation, write another valid command. like the read array command, the read identifier codes command functions independently of the v,, voltage and rp# must be vi,. following the read identifier codes command, the following information can be read: table 5. identifier codes code address manufacture code 00000 0000 1 data bo device code block status code 00002 00003 do l last erase operation completed successfully 1 dq,=o 1 *last erase operation did not completed successfully *reserved for future use note: dc&=1 dq3-, _ 1. x selects the specific block status code to be read. see figure 4 for the device identifier code memory map. 4.3 read status register command the status register may be read to determine when a block erase, full chip erase, (multi) word/byte write or block lock-bit configuration is complete and whether the operation completed successfully(see table 14). it may be read at any time by writing the read status register command. after writing this command, all subsequent read operations output data from the status register until another valid command is written. the status register contents are latched on the falling edge of oe# or ce#(either ce,# or ce,#), whichever occurs. oe# or ce#(either ce,# or ce,#) must toggle to vrh before further reads to update the status register latch. the read status register command functions independently of the v,, voltage. rp# must be vi,. the extended status register may be read to determine multi word/byte write availability(see table 14.1). the extended status register may be read at any time by writing the multi word/byte write command. after writing this command, all subsequent read operations output data from the extended status register, until another valid command is written. multi word/byte write command must be re-issued to update the extended status register latch. 4.4 clear status register command status register bits sr.5, sr.4, sr.3 and sr.l are set to ?1?s by the wsm and can only be reset by the clear status register command. these bits indicate various failure conditions (see table 14). by allowing system software to reset these bits, several operations (such as cumulatively erasing or locking multiple blocks or writing several bytes in sequence) may be performed. the status register may be polled to determine if an error occurs during the sequence. to clear the status register, the clear status register command @oh) is written. it functions independently of the applied v,, voltage. rp# must be vi,. this command is not functional during block erase, full chip erase, (multi) word/byte write block lock-bit configuration, block erase suspend or (multi) word/byte write suspend modes. rev. 1.9 sharp lhf16ka4 12 -- - 1.5 query command table 6. example of query structure output mode offset address output ;luery database can be read by writing query dq,5;-8 d&-n :ommand (98h). following the command write, read a,, a,, a,, a,, a,, a, ycle from address shown in table 7-l 1 retrieve the 1 , 0 , 0 , 0 , 0 , 0 (20h) high z ?q? xitical information to write, erase and otherwise x8mode 1 ,o,o,o,o,l (21h) highz ?q? :ontrol the flash component. a, of query offset 1, o,o,o,l ,0(22h) highz ?r? iddress is ignored when x8 mode (byte#=v,l). 1 , 0 , 0 , 0 , 1 , 1 (23h) high z ?r? a,, a,, a,, a,, a, juery data are always presented on the low-byte lata output (dqc-dq,). in x16 mode, high-byte :dqs-dq,s) outputs ooh. the bytes not assigned to iny information or reserved for future use are set to ?0?. this command functions independently of the j,, voltage. rp# must be vi,. 4 x16mode 1 ,o,o,o,o (10h) ooh ?q? 1 ,o,o,o,l (11h) ooh ?r? 1.5.1 block status register rhis field provides lock configuration and erase status for the specified block. these informations are only available nhen device is ready (sr.7=1). if block erase or full chip erase operation is finished irregulary, block erase status iit will be set to ?1 ?i. if bit 1 is ?l?, this block is invalid. table 7. query block status register offset (word address) length description (ba+2)h olh block status register bit0 block lock configuration o=block is unlocked 1 =block is locked uote: i? bit1 block erase status o=last erase operation completed successfully l 1 =last erase operation not completed successfully bit2-7 reserved for future use i. ba=the beginning of a block address. rev. 1.9 sharp ~. lhflgka4 13 . - -- - 4.5.2 cfi query identification string the identification string provides verification that the component supports the common flash interface specification. additionally, it indicates which version of the spec and which vendor-specified command set(s) is(are) supported. offset (word address) loh,llh,12h 13h,14h 15h,16h 17h,18h \ lsh,lah table 8. cfi query identification string length description 03h query unique ascii string ?qry? 51 h,52h,59h 02h primary vendor command set and control interface id code 01 h,ooh (scs id code) 02h address for primary algorithm extended query table 31 h,ooh (scs extended query table offset) 02h alternate vendor command set and control interface id code ooooh (ooooh means that no alternate exists) 02h address for alternate algorithm extended query table ooooh (ooooh means that no alternate exists) 4.53 system interface information the following device information can be useful in optimizing system interface software. table 9. system information string offset (word address) length description 1bh olh vc, logic supply minimum write/erase voltage 27h (2.7v) 1ch olh v,, logic supply maximum write/erase voltage 55h (5.5v) 1dh olh v,, programming supply minimum write/erase voltage 27h (2.7v) 1eh olh ./? u,, programming supply maximum write/erase voltage 55h (5.5v) 1fh .ol h typical timeout per single byte/word write 03h (23=8us) 20h 01h typical timeout for maximum size buffer write (32 bytes) 06h (26=64us) 21h olh typical timeout per individual block erase oah (oah=lo, 210=1 024ms)- 22h olh typical timeout for full chip erase / ofh (ofh=15, 215=32768ms) 23h olh maximum timeout per single byte/word write, 2n times of typical. 04h (24=1 6, 8usxl6=128us) 24h olh maximum timeout maximum size buffer write, 2n times of typical. 04h (24=16, 64usxl6=1024us) 25h olh maximum timeout per individual block erase, 2n times of typical. 04h (24=1 6,1024msxl6=16384ms) 26h olh maximum timeout for full chip erase, 2n times of typical. 04h (24=1 6,32768msxl6=524288ms) rev. 1.9 sharp lhf16ka4 14 . - 1.5.4 device geometry definition rhis field provides critical details of the flash device geometry. offset (word address) 27h 28h,29h 2ah,2bh 2ch 2dh,2eh 4 2fh,30h table 10. device geometry definition length description olh device size 15h (15h=2 1, 221 =2097152=2m bytes) 02h flash device interface description 02h,ooh (x8/x1 6 supports x8 and xl 6 via byte#) 02h maximum number of bytes in multi word/byte write 05h,ooh (2s=32 bytes ) olh number of erase block regions within device 01 h (symmetrically blocked) 02h the number of erase blocks 1 fh,ooh (1 fh=31 ==> 31+1=32 blocks) 02h the number of ?256 bytes? cluster in a erase block ooh,ol h (01 ooh=256 ==>256 bytes x 256= 64k bytes in a erase block) 1.5.5 scs oem specific extended query table zertain flash features and commands may be optional in a vendor-specific algorithm specification. the optional rendor-specific query table(s) may be used to specify this and other types of information. these structures are defined solely by the flash vendor(s). offset (word address) 31 h,32h,33h 34h 35h 36h,37h, 38h,39h ? 3ah 3bh,3ch 3dh 3eh 3fh table 11. scs oem specific extended query table length description 03h pri 50h,52h,49h olh 31 h (1) major version number , ascii olh 30h (0) minor version number, ascii 04h oj=h,ooh,ooh,ooh optional command support bito=l : chip erase supported bitl=l : suspend erase supported bit2=1 : suspend write supported bit3=1 : lock/unlock supported bit4=0 : queued erase not supported bit5-31=0 : reserved for-future use olh olh supported functions after suspend bito=l : write supported after erase suspend bit1 -7=o : reserved for future use 02h 03h,ooh block status register mask bito=l : block status register lock bit [bsr.o] active bitl=l : block status register valid bit [bsr.l] active b&z-15=0 : reserved for future use olh vcc logic supply optimum write/erase voltage(highest performance) 50h(5ov) olh v,, programming supply optimum write/erase voltage(highest performance) 50h(5.ov) reserved reserved for future versions of the scs specification rev. 1.9 sharp . - lhflgka4 15 -- - 4.6 block erase command block erase is executed one block at a time and initiated by a two-cycle command. a block erase setup is first written, followed by an block erase confirm. this command sequence requires appropriate sequencing and an address within the block to be erased (erase changes all block data to ffh). block preconditioning, erase and verify are handled internally by the wsm (invisible to the system). after the two-cycle block erase sequence is written, the device automatically outputs status register data when read (see figure 5). the cpu can detect block erase completion by analyzing the output data of the sts pin or status register bit sr.7. when the block erase is complete, status register bit sr.5 should be checked. if a block erase error is detected, the status register should be cleared before system software attempts corrective actions. the cui remains in read status register mode until a new command is issued. this two-step command sequence of set-up followed by execution ensures that block contents are not accidentally erased. an invalid block erase command sequence will result in both status register bits sr.4 and sr.5 being set to ?1?. also, reliable block erasure can only occur when vcc=vcc,,2 and vpp=vpph1. in the absence of this high voltage, block contents are protected against erasure. if block erase is attempted while v,,iv,,,,, sr.3 and sr.5 will be set to ?1?. successful block erase requires that the corresponding block lock-bit be cleared or if set, that wp#=v,,. if block erase is attempted when the corresponding? block lock-bit is set and wp#=vil, sr.l and sr.5 will be set.to ?1?. 4.7 full chip erase command this command followed by a confirm command (doh) erases all of the unlocked blocks. a full chip erase setup is first written, followed by a full chip erase confirm. after a confirm command is written, device erases the all unlocked blocks from block 0 to block 31 block by block. this command sequencr requires appropriate sequencing. bloc1 preconditioning, erase and verify are handlec internally by the wsm (invisible to the system). afte the two-cycle full chip erase sequence is written, tht device automatically outputs status register dat; when read (see figure 6). the cpu can detect ful chip erase completion by analyzing the output data o the sts pin or status register bit sr.7. when the full chip erase is complete, status registe bit sr.5 should be checked. if erase error i! detected, the status register should be cleared before system software attempts corrective actions. the cu remains in read status register mode until a nev command is issued. if error is detected on a bloc1 during full chip erase operation, wsm stops erasing reading the block valid status by issuing read ic codes command or query command informs whict blocks failed to its erase. this two-step command sequence of set-up followec by execution ensures that block contents are no accidentally erased. an invalid full chip erase command sequence will result in both status register bits sr.4 and sr.5 being set to ?1?. also, reliable ful chip erasure can only occur when vcc=vcc1,2 ant vpp=vpphi- in the absence of this high voltage, block contents are protected against erasure. if full chir erase is attempted while vpp~vpp,k, sr.3 and sr.e will be set to ?1?. when wp#=v,,, all blocks are erased independent of block lock-bits status. wher wp#=v,,, only unlocked blocks are erased. in this case, sr.l and sr.5 will not be set to ?1?. full chip erase can not be suspended. rev. 1.9 sharp . - lhf16ka4 16 4.8 word/byte write command word/byte write is executed by a two-cycle command sequence. word/byte write setup (standard 40h or alternate 10h) is written, followed by a second write that specifies the address and data (latched on the rising edge of we#). the wsm then takes over, controlling the word/byte write and write verify algorithms internally. after the word/byte write sequence is written, the device automatically outputs status register data when read (see figure 7). the cpu can detect the completion of the word/byte write event by analyzing the sts pin or status register bit sr.7. when word/byte write is complete, status register bit sr.4 should be checked. if word/byte write error is detected, the status register should be cleared. the internal wsm verify only detects errors for ?1?s that do not successfully write to ?0?s. the cui remains in read status register mode until it receives another command. reliable word/byte writes can only occur when vcc=vcc,,2 and vpp=vpph1. in the absence of this high voltage, memory contents are protected against word/byte writes. if word/byte write is attempted while v,+v,,l,, status register bits sr.3 and sr.4 will be set to ?1 ?i. successful word/byte write requires that the corresponding block lock-bit be cleared or, if set, that wp#=v,,. if word/byte write is attempted when the corresponding block lock-bit is set and wp#=v,l, sr.l and sr.4 will be set to ?1 ?i. word/byte write operations with v,lcwp#cv,, produce spurious results and shquld not be attempted. 4.9 multi word/byte write command multi word/byte write is executed by at least four- cycle or up to 35cycle command sequence. up to 32 bytes in x8 mode (16 words in x16 mode) can be oaded into the buffer and written to the flash array. first, multi word/byte write setup (e8h) is written with :he write address. at this point, the device automatically outputs extended status register data :xsr) when read (see figure 8, 9). if extended status register bit xsr.7 is 0, no multi word/byte nrite command is available and multi word/byte write setup which just has been written is ignored. to retry, continue monitoring xsr.7 by writing multi word/byte write setup with write address until xsr.7 transitions to 1. when xsr.7 transitions to 1, the device is ready for loading the data to the buffer. a word/byte couni (n)-1 is written with write address. after writing a word/byte count(n)-1, the device automatically turns back to output status register data. the wordlbyte count (n)-1 must be less than or equal to 1fh in x8 mode (ofh in x16 mode). on the next write, device start address is written with buffer data. subsequent writes provide additional device address and data depending on the count. all subsequent addres must lie within the start address plus the count. afte the final buffer data is written, write confirm (doh must be written. this initiates wsm to begin copyinf the buffer data to the flash array. an invalid mull word/byte write command sequence will result ir both status register bits sr.4 and sr.5 being set tc ?i ?. for additional multi word/byte write, write anothe multi word/byte write setup and check xsr.7. thf multi word/byte write command can be queue< while wsm is busy as long as xsr.7 indicates ?1? because LH28F160S5NS-L70 has two buffers. if ar error occurs while writing, the device will stop writin< and flush next multi word/byte write command loadec in multi word/byte write command. status register bi sr.4 will be set to ?1?. no multi word/byte write command is available if either sr.4 or sr.5 are se to ?1 ?i. sr.4 and sr.5 should be cleared before issuing multi word/byte write command. if a mult word/byte write command is attempted past an era.% block boundary, the device will write the data to flast array up. to an erase block boundary and then star writing. status register bits sr.4 and sr.5 will be se1 to ?1 ?i. reliable multi byte writes can only occur wher vcc=vcci12 and vpp=vpphi. in the absence of this high voltage, memory contents are protected againsl multi word/byte writes. if multi word/byte write is attempted while v,,sv,,l,, status register bits sr.3 and sr.4 will be set to ?1?. successful multi word/byte write requires that the corresponding block lock-bit be cleared or, if set, that wp#=v,,. if multi byte write is attempted when the corresponding block lock-bit is set and wp#=v,l, sr.l and sr.4 will be set to ?1 ?i. rev. 1.9 sharp lhflgka4 17 . - .- _- 1.10 block erase suspend command the block erase suspend command allows block- erase interruption to read or (multi) word/byte-write data in another block of memory. once the block- 3rase process starts, writing the block erase suspend command requests that the wsm suspend :he block erase sequence at a predetermined point in :he algorithm. the device outputs status register data nhen read after the block erase suspend command s written. polling status register bits 93.7 and sr.6 :an determine when the block erase operation has 3een suspended (both will be set to ?1?). sts will also transition to high z. specification twhrh2 defines :he block erase suspend latency. 4t this roint, a read array command can be written :o read data from blocks other than that which is suspended. a (multi) word/byte write command sequence can also be issued during erase suspend :o program data in other blocks. using the (multi) rnord/byte write suspend command (see section 1.1 l), a (multi) word/byte write operation can also be suspended. during a (multi) word/byte write operation nith block erase suspended, status register bit sr.7 nili return to ?0? and the sts (if set to ry/by#) output will transition to vol. however, sr.6 will *emain ?1? to indicate block erase suspend status. the only other valid commands while block erase is suspended are read status register and block erase resume. after a block erase resume :ommand is written to the flash memory, the wsm nili continue the block erase process. status register ,its sr.6 and sr.7 will automaticajly clear and sts nili return to vol. after the erase resume command s written, the device automatically outputs status ,egister data when read ?(see figure 10). vpp must *emain at vp,+,, (the same v,, level used for block xase) while block erase is suspended. rp# must ais0 remain at v,,. block erase cannot resume until (multi) word/byte write operations initiated during block erase suspend have completed. 4.11 (multi) word/byte write suspend command the (multi) word/byte write suspend command allows (multi) word/byte write interruption to read data in other flash memory locations. once the (multi) word/byte write process starts, writing the (multi) word/byte write suspend command requests that the wsm suspend the (multi) word/byte write sequence at a predetermined point in the algorithm. the device continues to output status register data when read after the (multi) word/byte write suspend command is written. polling status register bits sr.7 and sr.2 can determine when the (multi) word/byte write operation has been suspended (both will be set to ?1?). sts will also transition to high z. specification twhrr+ defines the (multi) word/byte write suspend latency. at this point, a read array command can be written to read data from locations other than that which is suspended. the only other valid commands while (multi) word/byte write is suspended are read status register and (multi) word/byte write resume. after (multi) word/byte write resume command is written to the flash memory, the wsm will continue the (multi) word/byte write process. status register bits sr.2 and sr.7 will automatically clear and sts will return to vol. after the (multi) word/byte write command is written, the device automatically outputs status register data when read (see figure 11). v,, must remain at vpph1 (the same v,, level used for (multi) word/byte write) while in (multi) word/byte write suspend mode. wp# must also remain at v,, or yl. rev.1.9 . - lhflgka4 18 .- - 4.12 set block lock-bit command a flexible block locking and unlocking scheme is enabled via block lock-bits. the block lock-bits gate program and erase operations with wp#=v,,+ individual block lock-bits can be set using the set block lock-bit command. see table 13 for a summary of hardware and software write protection options. set block lock-bit is executed by a two-cycle command sequence. the set block lock-bit setup along with appropriate block or device address is written followed by either the set block lock-bit confirm (and an address within the block to be locked). the wsm then controls the set block lock-bit algorithq. after the sequence is written, the device automatically outputs status register data when read (see figure 12). the cpu can detect the completion of the set block lock-bit event by analyzing the sts pin output or status register bit sr.7. when the set block lock-bit operation is complete, status register bit sr.4 should be checked. if an error is detected, the status register should be cleared. the cui will remain in read status register mode until a new command is issued. this two-step sequence of set-up followed by execution ensures that block lock-bits are not accidentally set. an invalid set block lock-bit command will result in status register bits sr.4 and sr.5 being setto ?1 ?i. also, reliable operations occur drily when vcc=vccj,2 and vpp=vpph,. in the absence of this high voltage, block lock-bit contents are protected against alteration. 4 successful set block ?lock-bit operation requires np#=v,,. if it is attempted with wp#=v,,, sr.l and jr.4 will be set to ?1? and the operation will fail. set ilock lock-bit operations with wp# shari= lhflgka4 20 - .- - table 14. status register definition wsms 1 bess / ecblbs 1 wsblbs 1 vpps 1 wss dps r 1 1 7 6 5 4 sr.7 = write state machine status 1 = ready 0 = busy sr.6 = block erase suspend status 1 = block erase suspended 0 = block erase in progress/completed sr.5 = erase and clear block lock-bits status 1 = error in erase or clear bloc1 lock-bits 0 = successful erase or clear block lock-bits 4 sr.4 = write and set block lock-bit status 1 = error in write or set block lock-bit 0 = successful write or set block lock-bit sr.3 = v,, status 1 = v,, low detect, operation abort o=v,,ok sr.2 = write suspend status 1 = write suspended 0 = write in progress/completed sr.l = device protect status 1 = block lock-bit and/or wp# lock detected, operation abort 0 = unlock? sr.0 = reserved for future?enhancements 3 2 1 0 notes: check sts or sr.7 to determine block erase, full chip erase, (multi) word/byte write or block lock-bit configuration completion. sr.6-0 are invalid while sr.7=?0?. if both sr.5 and sr.4 are ?1 ?s after a block erase, full chip erase, (multi) word/byte write, block lock-bit configuration or sts configuration attempt, an improper command sequence was entered. sr.3 does not provide a continuous indication of v,, level. the wsm interrogates and indicates the v,, level only after block erase, full chip erase, (multi) word/byte write or block lock-bit configuration command sequences. sr.3 is not guaranteed to reports accurate feedback only when v,,+v,,,, . sr.l does not provide a continuous indication of block lock-bit values. the wsm interrogates block lock-bit, and wp# only after block erase, full chip erase, (multi) word/byte write or block lock-bit configuration command sequences. it informs the system, depending on the attempted operation, if the block lock-bit is set and/or wp# is not v,,. reading the block lock configuration codes after writing the read identifier codes command indicates block lock-bit status. sr.0 is reserved for future use and should be masked out when polling the status register. sms r table 14.1. extended status register definition r i r r r r r 7 6 5 4 3 2 1 0 notes: xsr.7 = state machine status 1 = multi word/byte write available 0 = multi word/byte write not available after issue a multi word/byte write command: xsr.7 indicates that a next multi word/byte write command is available. xsr.g-o=reserved for future enhancements xsr.g-0 is reserved for future use and should be masked out when polling the extended status register. rev. 1.9 shari= lhf16ka4 21 r check if desired full status check procedure (7) ) command i write read statis register data-70h addhx read standby status register data check sr.7 l-wsm ready 0swsm busy wnte erase setup data-zoh addhwithin block to be erased i write erase confirm data-doh add-within block to be erased i read / / status register data standby check sr.7 l=wsm ready 0.xwsm busy repeat for subsequent block erasures. full stake check can be done after each block erase or after a sequence of block erasures. write ffh after the last operation to place device in mad array mode. bus operation command i standby check sr.3 t=vpp error detect standby check sr.4.5 both l=command sequence error i standby check sr.5 l-block erase error srs.sr.4.sr.3 and sr.l am only cleared by the clear status register command in casas where multiple blocks am emsed if ermr is detected. clear the status register before attempting figure 5. automated block erase flowchart rev. 1.9 sharp - lhflgka4 22 _ - (-y-) check if desired complete full status check procedure read status register data(see above) command write read status register data=70h addr=x 1 read 1 1 status register data i i i i i i standby check sr.7 l.wsm ready o-wsm busy write write full chip erase s-jp full chip erase conflml data-3oh ad&-x data-doh add-x read status register data i full stalls check can b-a done after each full chip erase. write ffh after tie last operation to place device in read army mode. command comments standby chedc sr.3 lavpp error detect standby check sr.4,5 both 1 -command sequence error standby check sr.5 l-full chip erase error srs.sr.4.sr.3 and sr.l are only deared by the clear status register command in cases where multiple blocks are erased before full status is checked. if enw is detected, clear the st&e register before attempting retry or other error recovery. figure 6. automated full chip erase flowchart rev. 1.9 read stahls reglrter 23 0 sr.7= . &, data and address check if desired full status check procedure read status register data(see above) dwce protect error bus operation command commanb write read standby read status register data=70h addr-x status register data check sr.7 1 -wsm rea&+ o=wsm bury wiite wlfte setup word/byte write wordbyte write data-40h or 1oh addr-location to be written data-data to be written addr-location to be wlitten read standby status register data check sr.7 l=wsm ready o=wsm busy repeat for subsequent wotiyte writes. sr full status check can be done after each wordmyte write. or after a sequence of wmdhyte writes. write ffh after the last word/byte write operation to place device m read array mode. bus operation command commenla standby check sr.3 l=vp, error detect check sr.1 standby l=device protect detect wpx=v,$jock lock-bit is set only required for systems implementing lock-bit configuration standby check sr.4 l-data write error sr.4.sr.3 and sr.l are only cleared by the clear status ragstar command in cases where multiple lxabons are wtftten before full status is checked. if error is detected, clear the status register before attempbng retry or other error recovery. figure 7. automated word/byte write flowchart rev. 1.9 sharp lhflgka4 read extend status register write anotier block address write buffer data, device address multi word/byte write abort bus operation command commenk wlik setup datape3f-l multi wordlbyte write addr=stwt address read standby extended status register data check xsr.7 1rmulti wml/byk wtite ready o=mjlti wodmyk write busy write (nokl) write (note2.3) write (note4.5) write data-word or byte count (n)-1 add&tart address data=buffer data addr-start address data=buffer data addrpdevice address data=doh addr-x read status register data standby check sr.7 i=wsm ready oiwsm busy 1, byte or word count values on dq,., are loaded into the count register. 2. write buffer contents will be programmed at the start address. 3. align the start address on a write buffer boundary for mamum programming performance. 4.the device aborts the multi word/byte write command if the current address is oukide of the original blockaddress. b.the status register indicates an ?improper command sequence? if the multi word/byte command is aborted. follow this with a clear status register command. sr lull status check can be done after each multi word/byte write. or after a sequence of multi wonvbyte writes. write ffh afterthe last multi w&byte write operation to place device in read army mode. figure 8. automated multi word/byte write flowchart rev. 1.9 shari= lhflgka4 25 _- full status check procedure for multi word/byte write operation device protect enor i bus operalion command comments standby check sr.3 l-vp,, error detect standby check sri l=dovica protect detect wp#+,block lock-bit is set only required for systems implementing lock-bit configuration standby check sr.4.5 both l-command sequence error standby check sr.4 14ata write error srs.sr.4.sr.3 and sr.1 are only deared by the clear status register command in cases where multiple locations are written before full status is checked. ?f ermr)s detected, clear the status regtstar before attempting retry or other efmr reccnery. figure 9. full status check procedure for automated multi word/byte write rev. 1.9 lhflgka4 read c\i- sr.7= 0 1 reed status ragistar data addr.=x standby check sr.7 1 -wsm rea&y o-wsm busy standby check sr.6 l-block erase sutpwded o-block ease completed write data-wi-l addr-x figure io. block erase suspend/resume flowchart rev.1.9 shari= lhf16ka4 27 stall =i_i write 5x4 read status register 3 sr.73 o 1 (multi) woldmte write\ complel ted command (multi) wonvbyta wntc suspend read standby comments data-soh addhx status register data addr-x check sr.7 l=wsm rea* oiwsm busy check sr.2 l=(mljlti) wo#syte write suspendsd ow(multl) word/byte write completed data..ffh addhx read array lccatiis other than that being written. data-doh addr-x figure 11. (multi) word/byte write suspend/resume flowchart rev. 1.9 shari= lhflgka4 check if desired set block lock-sit full status check procedure command i write sat block lock-bit selup data-6oh add&lock address i set block 1 datazolh. write lock-bit confirm add&lock address repeat for subsequent block lock-bit set operations. full status cback can be done after each block l&-bit set operation or after a sequence of block lock-bit sat operabns. wri!e ffh after the last block lock-bit sat operation to place device in read array mode. command standby check sr.3 l=vpp error detect srs.sr.4.sr.3 and sr.1 are only cleared by the clear status register command in cases where multiple mock lock-bits are set before figure 12. set block lock-bit flowchart 1 rev. 1.9 sharp lhf16ka4 29 wlite 60h write doh full status check if dewed clear block lock-sits complete full status check procedure read status register data(see above) write clear block lock-bits confinn data-doh add-x read standby slatus register data check sr.7 l=wsm ready o=wsm busy write ffh after the clear block lock-bits operation to place device in read army mode. bus opsmioll command j standby 1 check sr.3 i-vpp error detect check sr.l l-device protect detect wp%.v,l i i srs,sr.4.sr.3 and sr.l are only cleared by the clear status register command. if enor is detected, clear the status register before attempting mhy or other envr recovery. figure 13. clear block lock-bits flowchart rev. 1.9 shari= lhflgka4 30 .- - 5 design considerations 5.1 three-line output control the device will often be used in large memory arrays. sharp provides three control inputs to accommodate multiple memory connections. three- line control provides for: a. lowest possible memory power dissipation. b. complete assurance that data bus contention will not occur. to use these control inputs efficiently, an address decoder should enable ce# while oe# should be connected to all memory devices and the system?s read#,control line. this assures that only selected memory devices have active outputs while deselected memory devices are in standby mode. rp# should be connected to the system powergood signal to prevent unintended writes during system power transitions. powergood should also toggle during system reset. 5.2 sts and block erase, full chip erase, (multi) word/byte write and block lock-bit configuration polling sts is an open drain output that should be connected to vcc y b a pullup resistor to provide a hardware method of detecting block erase, full chip erase, (multi) word/byte write and block lock-bit configuration completion. in default mode, it transitions low after block erase, full chip erase, (multi) word/byte write or block lock-bit configuration commands and returns to v,, when the wsm has finished executing the. internal algorithm. for alternate sts pin configurations, see the configuration command. sts can be connected to an interrupt input of the system cpu or controller. it is active at all times. sts, in default mode, is also high z when the device is in block erase suspend (with (multi) word/byte write inactive), (multi) word/byte write suspend or deep power-down modes. 5.3 power supply decoupling flash memory power switching characteristics require careful device decoupling. system designers are interested in three supply current issues; standby current levels, active current levels and transient peaks produced by falling and rising edges of ce# and oe#. transient current magnitudes depend on the device outputs? capacitive and inductive loading. two-line control and proper decoupling capacitor selection will suppress transient voltage peaks. each device should have a o.luf ceramic capacitor connected between its vcc and gnd and between its v,, and gnd. these high-frequency, low inductance capacitors should be placed as close as possible to package leads. additionally, for every eight devices, a 4.7uf electrolytic capacitor should be placed at the array?s power supply connection between voc and gnd. the bulk capacitor will overcome voltage slumps caused by pc board trace inductance. 5.4 vpp trace on printed circuit boards updating flash memories that reside in the target system requires that the printed circuit board designer pay attention to the v,, power supply trace. the v,, pin supplies the memory cell current for block erase, full chip erase, (multi) word/byte write and block lock-bit configuration. use similar trace widths and layout considerations given to the vcc power bus. adequate v,, supply traces and decoupling will decrease v,, voltage spikes and overshoots. rev. 1.9 sharp lhflgka4 31 .- - 5.5 vcc, vpp, rp# transitions block erase, full chip erase, (multi) word/byte write and block lock-bit configuration are not guaranteed if v,, falls outside of a valid v,,,, range, vcc falls outside of a valid vcc,,2 range, or rp#=v,,. if v,, error is detected, status register bit sr.3 is set to ?1? along with sr.4 or sr.5, depending on the attempted operation. if rp# transitions to v,, during block erase, full chip erase, (multi) word/byte write or block lock-bit configuration, sts(if set to ry/by# mode) will remain low until the reset operation is complete. then, the operation will abort and the device will enter deep power-down. the aborted operation may leave data partially altered. therefore, the command sequence must be repeated after normal operation is restored. device power-off or rp# transitions to v,, clear thd status register. the cui latches commands issued by system software and is not altered by v,, or ce# transitions or wsm actions. its state is read array mode upon power-up, after exit from deep power-down or after vcc transitions below v,ko. after block erase, full chip erase, (multi) word/byte write or block lock-bit configuration, even after v,, transitions down to vpplk, the cui must be placed in read array mode via the read array command if subsequent access to the memory array is desired. 5.6 power-up/down protection the device is designed to offer protection against accidental block and full chip erasure, (multi) word/byte writing or block lock-bit configuration during dower transitions. upon power-up, the device is indifferent as to which power supply (v,, or voc) powers-up first. internal circuitry resets the cui tc read array mode at power-up. a system designer must guard against spuriou: writes for vco voltages above vlko when v,, iz active. since both we# and ce# must be low for i command write, driving either to v,, will inhibit writes the cul?s two-step command sequence architecture provides added level of protection against datz alteration. in-system block lock and unlock capability prevent: inadvertent data alteration. the device is disablec while rp#=v,, regardless of its control inputs state. 5.7 power dissipation when designing portable systems, designers mus consider battery power consumption not only during device operation, but also for data retention during system idle time. flash memory?s nonvolatilib increases usable battery life because data is retainec when system power is removed. in addition, deep power-down mode ensures extremely low power consumption even when systerr power is applied. for example, portable computing products and other power sensitive applications thal use an array of devices for solid-state storage car consume negligible power by lowering rp# to vi, standby or sleep modes. if access is again needed. the devices can be read following the t,hqv ant tphwl wake-up cycles required after rp# is firsi raised to v,,. see ac characteristics- read only and write operations and figures 17, 18, 19, 20 for more information. rev. 1.9 sharp lhflgka4 32 . - -- - 6 electrical specifications 6.1 absolute maximum ratings* operating temperature during read, erase, write and block lock-bit configuration . . . . . . ..o?c to +70?c(1) temperature under bias . . . . . . . . . . . . . . . -10c to +8o?c storage temperature . . . . . . . . . . . . . . . . . . . . . . . . -65c to +125?c voltage on any pin (except vcc, v,,) . . . . . . . . . . . . . . . -09 to vcc+0.5v(2) v,, suply voltage . . . . . . . . . . . . . . . . . . . . . . . . . . . . -0.2v to +7.ov(2) v,, upgate voltage during erase, write and block lock-bit configuration . . . . ..-0.2v to +7.0vt2) output short circuit current . . . . . . . . . . . . . . . . . . . . . . . . 1 00ma(3) *warning: stressing the device beyond the ?absolute maximum ratings? may cause permanent damage. these are stress ratings only. operation beyond the ?operating conditions? is not recommended and extended exposure beyond the ?operating conditions? may affect device reliability. notes: 1. operating temperature is for commercial temperature product defined by this specification. 2. all specified voltages are with respect to gnd. minimum dc voltage is -0.5v on input/output pins and -0.2v on vcc and v,, pins. during transitions, this level may undershoot to -2.ov for periods <20ns. maximum dc voltage on input/output pins and vcc is vcc+osv which, during transitions, may overshoot to vcc+2.ov for periods <20ns. 3. output shorted for no more than one second. no more than one output shorted at a time. 6.2 operating conditions temperature and vcc ouerating conditions symbol parameter min. max. unit test condition ta operating temperature 0 +70 ?c ambient temperature vnc, vnr: supply voltage (5vio.25v) 4.75 5.25 v ~ v(-y vno supply voltage (5v+o.5v) 4.50 5.50 v 6.2.1 capacitance(l) ,, symbol parameter. c,n input capacitance cn, ,t output capacitance vote: i. sampled, not 100% tested. t,=+25?c, f=l mhz typ. max. 7 10 9 12 unit condition pf v,,=o.ov pf vn, ,t=o.ov rev. 1.9 sharp lhfl6ka4 33 _- . . i 2.2 ac input/output test conditions ac test inputs are driven at 3.ov for a logic ?1? and o.ov for a logic ?0.? input timing begins, and output timing ends, at 1.w. input rise and fall times (10% to 90%) cl 0 ns. figure 14. transient input/output reference waveform for vcc=5v*0.25v (high speed testing configuration) 4 o~t-)(--pzfzy)(yr ac test inputs are driven at voh (2.4 vttl) for a logic ?1? ahd vol (0.45 vtl) for a logic ?0.? input timing begins at vih (2.0 vttl) and vil (0.8 vttl). output timing ends at vih and vil. input rise and fall times (10% to 90%) ~10 ns. figure 15. transient input/output reference waveform for vcc=uko.5v (standard testing configuration) device undeq test 0 out cl includes jib capacitance - figure 16. transient equivalent testing load circuit test confi uration ca acitance loadin value n rev. 1.9 shari= lhf16ka4 34 -- - 5.2.3 dc characteristics dc characteristics vccz5v test symbol parameter notes typ- max. unit conditions ?ll input load current 1 *l ija v,,=vccmax. v,,=vcc or gnd ?lo output leakage current 1 *lo ija ;~?;vccma* =vcc or gnd ?cc, vcc standby current 1,396 cmos inputs 25 100 cia v,,=v,,max. ce#=rp#=v,,i0.2v ttl inputs 2 4 ma v,,=v,,max. ce#=rp#=v,,, ?ccd v,, deep power-down 1 15 rp#=gnd*o.2v 4 current ija lout(sts)=oma ?ccr v,, read current 156 cmos inputs 50 ma vcc=vccmax. ce#=gnd f=8mhz, lout=oma ttl inputs 65 ma vcc=vccmax., ce#=v,, f=8mhz, lo,,,=oma ?ccw vcc write current 1,7 ((multi) w/b write or set block 35 ma v,,=5.ov~o.5v lock bit) ?cc, v,, erase current 1,7 (block erase, full chip erase, 30 ma vpp=5.ov*o.5v clear block lock bits) ?ccws v,, write or block erase 12 ii;cfs suspend current 1 10 ma ce#=v,, ?pps vp, standbycurrent 1 *2 *15 ija v,,iv,, lnnn v&read current 1 10 200 pa vpp>vcc ?ppd vp, deep power-down 1 current 0.1 5 pa rp#=gndk0.2v ippw vp, write current 1,7 ((multi) w/b write or set block 80 ma vpp=5.ov*o.5v lock bit) ?ppe vp, erase current 1,7 (block erase, full chip erase, 40 ma vpp=5.ov+o.5v clear block lock bits) ?ppws vp, write or block erase 1 ippfs , suspend current 10 200 ija vpp=vpphl i rev. 1.9 shari= lhflgka4 35 symbol v,, -. - parameter input low voltage input high voltage output low voltage dc characteristics (continued) vcc=5v notes min. ( max. 7 -0.5 0.8 unit v test conditions 7 2.0 vcc +0.5 v 397 n ak \i vcc=vccmin. ?oh1 voh2 output high voltage u-w output high voltage (cmos) ?.-tj ? lol=5.8ma 397 2.4 v vcc=v,,min. i,,=-2sma 3,7 0.85 vcc=vccmin. vcc v ioh=-2.!%la vcc -0.4 v il,,=v,omin. m=-l ooua ?pplk i vp, lockout during normal operations i 4v7 i i 1.5 r-v -/- vpph1 ? vp, during write or erase operations v, ko vc, lockout voltage iotes: 4.5 5.5 v 2.0 v all currents are in rms unless otherwise noted. typical values at nominal v,, voltage and ta=+25?c. !i i ccws and ?cces are specified with the device de-selected. if read or byte written while in erase suspend mode, the device?s current draw is the sum of i,,,, or icces and i,,, or lccw, respectively. i. includes sts. . . block erases, full chip erases, (multi) word/byte writes and block lock-bit configurations are inhibited when vpplvpplk, and not guaranteed in the range between vpplk(max.) and vpph, (min.) and above vpph, (max.). i. automatic power savings (aps) reduces typical lo,, to 1 ma at 5v voo in static operation. i. cmos inputs are either vccf0.2v or gndko.2v. ttl inputs are either vi, or vi,. ?. sampled, not 100% tested. rev. 1.9 shari= lhf16ka4 36 6.2.4 ac characteristics - read-only operations(?) vcc=svdl5v, 5vko.25v, ta=o?c to +70x vcc=5v+q.25v lh28f16os5-l70@) versiond4) v~,r.=5v*o.5v lh28fi 6os5-l80@) sym. 1 parameter 1 notes min. 1 max. min. 1 max. unit notes: 1. see ac input/output reference waveform for maximum allowable input slew rate. 2. oe# may be delayed up to telov-&ov after the falling edge of ce# without impact on t,lqv. 3. sampled, not 100% tested. 4. see ordering information for device speeds (valid operational combinations). 3. see transient input/output reference waveform and transient equivalent testing load circuit (high speed configuration) for testing characteristics. 3. see transient input/output reference waveform and transient equivalent testing load circuit (standard configuration) for testing characteristics. rev. 1.9 sharp lhflgka4 37 device address selection address stable rc kvav k vih ce#(e) ml vih oe#(g) ml we#(w) vil voh data( d/q) vol kc rp#(p) ml note: ce# isdefined as the latter of ceo# and ce,# going low or the first of ceo# or ce1# going high. figure 17. ac waveform for read operations rev. 1.9 shari= .- lhflgka4 38 device address selection address stable vih oe#(g) wl {vlh tflclv=tavqv byte#(f) vil l . ..s*..*.- voh data d/cl) &l pqo- 7) vol high z data output ::::::::::$i?& high z voh data( d/q) high z pqdqd vol note: ce# is defined as the latter of ceo# and ce,# going low or the first of ceo# or ce,# going high. figure 18. byte# timing waveforms rev. 1.9 lhf16ka4 39 6.2.5 ac chariicteristics - write operations(?) vcc=5vdmv, 5ko.25v, t,,=o?c to +70x vcc=5v*0.25v lh28f16os5-l70@) versions@) v~~=5v*o.5v lh28fl 60s5-l80(7) sym. i parameter 1 notes min. 1 max. min. 1 max. unit tavnv 1 write cycle time 70 80 ns tphwl tf, ,,,,, 1 ce# setup to ? tvpww 1 vpp setup to w tnvwcr 1 data setup to w &,,-,y 1 data hold from we# high high recovery to we# going twhr, we# high to sl twhn, write recovery before read 0 0 ns bwl vp,, hold from valid srd, sts high z 2,4 0 0 ns tavsl wp# v uinh 71h hold from valid srd, sts 2,4 0 0 ns , i llljli l i i i i i i notes: 1. read timing characteristics during block erase, full chip erase, (multi) wrod/byte write and block lock-bit configuration operations are the same as during read-only operations. refer to ac characteristics for read-only operations. 2. sampled, not 100% tested. 3. refer to table 4 for valid a,, and din for block erase, full chip erase, (multi) word/byte write or block lock-bit configuration. 4. vpp should be held at vpph, until determination of block erase, full chip erase, (multi) word/byte write or block lock-bit configuration success (sr.1/3/4/5=0). 5. see ordering information for device speeds (valid operational combkrations). 6. see transient input/output refecence waveform and transient equivalent testing load circuit (high seed configuration) for testing characteristics. 7. see transient input/output reference waveform and transient equivalent testing load circuit (standard configuration) for testing characteristics. rev. 1.9 shari= lhfl6ka4 40 1 2 3 4 5 6 #--i----- addresses(a) ce#(e) oe#(g) wew?) data(d/q) sts(r) wp#(s) rp#(p) ::: j= vpphl vpp(v) vpplk notes: 1. vcc power-up and standby. 2. write erase or write setup. vil- ??????????????ru 3. write erase donfirm or,valid address and data. 4. automated erase or program delay. 5. read statusregister data. 6. write readarray command. 7. ce# is defined as the latter of ceo# and ce1# going low or the first of ceo# or cei# going high. figure 19. ac waveform for we#-controlled write operations rev. 1.9 lhflgka4 41 6.2.6 alternafliie ce#-controlled writes(l) vcc=5v*0.5v, 5v*o.25v, ta=o?c to +7o?c vcc=5vi0.25v lh28f16os5-l70@) v~~=5v*osv lh28fl 60s5-l80(7) notes: 1. in systems where ce# defines the write pulse width (within a longer we# timing waveform), all setup, hold and inactive we# times should be measured relative to the ce# waveform. 2. sampled, not 100% tested. 3. refer to table 4 for valid a,, and d,, for block erase, full chip erase, (multi) word/byte write or block lock-bit configuration. 4. vp, should be held at vpph1 until determination of block erase, full chip erase, (multi) word/byte write or block lock-bit configuration success (sr.1/3/4/5=0). 5. see ordering information for device speeds (valid operational combinations). 5. see transient input/output reference waveform and transient equivalent testing load circuit (high seed configuration) for testing characteristics. 7. see transie,nt input/output reference waveform and transient equivalent testing load circuit (standard configuration) for testing characteristics. rev. 1.9 sharp lhflgka4 42 -- r addresses(a) we#(w) oe#(g) ce#(e) data( d/q) 4 sts(r) wp#(s) notes: 1. vcc power-up and standby. 2. write erase or write setup. 3. write erase confirm or.valid address and data. 4. automated erase or pragram delay. 5. read status,register data. 6. write readarray command. 7. ce# is defined as the latter of ceo# and ce,# going low or the first of ceo# or ce1# going high. figure 20. ac waveform for ce#-controlled write operations rev. 1.9 shari= .- lhflgka4 43 high z sts(r) vol vih rp#(p) vil (a)reset during read array mode high z sts( r) vol . tplrh vih rp#( p) \ wl r 4 - blph (b)reset during block erase, full chip erase, (multi) word/byte write or block lock-bit configuretion vcc rp#(p) 5v vil vih vil i i - t5vph . i i- (c)vcc power up timing -- - 6.2.7 reset operations figure 21. ac waveform for reset operation reset ac specifications. vn,=5v i. symbol parameter notes min. max. unit tplph rp# pulse low time (if rp# is tied to voc, this specification is not applicable) 100 ns tplrh rp# low to reset during block erase, full chip erase, (multi) word/byte write or block lock-bit configuration 12 13.1 ijs tg?ph vcc at 4.5v to rp# high 3 100 ns 1 uotes: i. if rp# is asserted while a block erase, full chip erase, (multi)-word/byte write or block lock-bit configuration operation is not executing, the reset will complete within loons. !. a reset time, tphqv, is required from the latter of sts going high z or rp# going high until outputs are valid. 3. when the device power-up, holding rp# low minimum 100ns is required after vcc has been in predefined range and also has been in stable there. rev. 1.9 sharp - lhflgka4 44 6.2.8 block efiise, full chip erase, (multi) word/byte write and block lock-bit configuration performance@) t wkm tfh(j?g set block lock-bit time 2 9.24 120 ijs t wi-k&m tfhn?d clear block lock-bits time 2 0.34 10 s ?whnhl f&qqrh, write suspend latency time to read 5.6 7 ijs phnr-f2 erase suspend latency time to read 9.4 13.1 ljs fhrh? notes: 1. typical values measured at ta=+25?c and nominal voltages. assumes corresponding block lock-bits are not set. subject to change based on device characterization. 2. excludes system-level overhead. 3. sampled but not 100% tested. rev. 1.9 shari= lhflgka4 45 _ - -- - additional information ,l ordering information product line designator for all sharp flash products i i i il/h~2181fi1/6/o/s15~h1/nsi-/l17lo~ 160 = 16-mbit p- u l-rl device density access speed (ns) 70:70ns (5v,3opf), 80ns (5v) architecture 10: 1 oons (5v) s = regular block package power supply type t = 56-lead tsop 5 = smart 5 technology r = 56-lead tsop(reverse bend) ns = 56-lead ssop operating temperature b = 64-ball csp blank = 0c - +7o?c :,,1 d = 64-lead sdip h = -40c - +85?c valid operational combinations v~~=5v*o.5v vcc=5v*0.25v 1 oopf load, 3opf load, jption order code ttl l/o levels 1.5v i/o levels 1 LH28F160S5NS-L70 lh28f16os5l80 lh28f160s5-l70 .i? rev. 1.9 shari= lhf16ka4 46 flash memory li@xxkxx family data protection noises having a level exceeding the limit specified in the specification may be generated under specific operating conditions on some systems. such noises, when induced onto we# signal or power supply, may be interpreted as false commands, caus ing undesired memory updat ing. to protect the data stored in the flash memory against unwanted overwriting, systems operating with the flash memory should have the following write protect designs, as appropriate: 1) protecting data in specific block setting the lock bit of the desired block and pul ling wp# low d isab ?les the writing operation on that block. by using this feature, the flash memory space can be divided into, for example, the program section(locked, section) and data section(unlocked section). by controlling wpst, desired blocks can be locked/unlocked through the software. for further information on setting/resetting block bit, refer to the specificati (see chapter 4.12 and 4.13.) 2) data protection through vpp on. i when the level of vpp is lower than vpplk (lockout voltage), write operation on the flashmemory is disabled. allblocksare lockedandthedata intheblocksarecompletely write protected. for the lockout voltage, refer to the specification. (see chapter 6.2.3. > 3) data protection through rp# when the rp# is kept low during power up and power down sequence such as voltage transition, write operation on the flash memory is- disabled, write protecting all blocks. for the detai is of rp# control, refer to the specification. (see chapter 5.6 and 6.2.7.) rev 1.9 sharp lhf16ka4 47 -- - lh28f16osxx-lxx flash memory errata 1. multi word/byte write operations problem; when two planes of 32-byte page buffer are both in full and first buffer data are being written to the flash array, the extended status register bit xsr.7 may be erroneously set to ?l?, which indicates the multi word/byte write command is available. workaround (1) u8e one page buffer after writing the data by the multi word/byte write command, the status register must be read to check the bit sr.7. at this point, the device is in read status register mode whether the read status register command is written or not. after the status register bit sr.7 is set to ?l?, the next multi word/byte write command will be available. (2) use two page buffers after writing the data in two planes by the multi word/byte write command, the status register must be read to check the bit sr.7. at this point, the device is in read status register mode whether the read status register command is written or not. after the status register bit sr.7 is set to ?l?, the next multi word/byte write command will be available. sharp .- lhf16ka4 48 -- - lh28fl6osxx-lxx flash memory errata use one page buffer use two page buffers .,.? no multi word/byte write command sequence full status check if desired 1 multi command sequence + write e8h i read xsr i write buffer data, device address sharp _- related docuhiekt informatioti?) document no. document name ap-#l-sd-e flash memory family software drivers ap-006-p-r-e data protection method of sharp flash memory i-- i ap-o07sw-e rp#, vpp electric potential switching circuit -1 note : 1. international customers should contact their local sharp or distribution sales o5ce. shari= iprellh,llnary see detail a pig. xasx plaue detail a 3% i ?i - k {yk / tin-leac m%$ l7xir 1h?-:im%ft, 4 ~2z?#~dtt4 d me i ssop56-p-600 lead finish i plating note plastic body dimensions do not include burr 4m [ of resin. mawing no. i aa2021 unit j mm |
Price & Availability of LH28F160S5NS-L70
 |
|
|
|
|
All Rights Reserved © IC-ON-LINE 2003 - 2022 |
| [Add Bookmark] [Contact Us] [Link exchange] [Privacy policy] |
|
Mirror Sites : [www.datasheet.hk]
[www.maxim4u.com] [www.ic-on-line.cn]
[www.ic-on-line.com] [www.ic-on-line.net]
[www.alldatasheet.com.cn]
[www.gdcy.com]
[www.gdcy.net] |